Industrial machine management system, method for managing industrial machine, and non-transitory computer-readable storage medium

ABSTRACT

An industrial machine management system includes circuitry that collects changeable setting data of an industrial machine, determines, based on the setting data at each time point of multiple time points, whether a change has been made to the setting data, obtains change information regarding the change when the change is determined as having been made to the setting data, determines whether a predetermined event has occurred in the industrial machine, identifies, when the predetermined event is determined as having occurred, the change information such that the change information is related to the predetermined event, and outputs the change information that is identified.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority under 35 U.S.C. § 119 toJapanese Patent Application No. 2019-012166, filed Jan. 28, 2019. Thecontents of this application are incorporated herein by reference intheir entirety.

BACKGROUND Field of the Invention

The embodiments disclosed herein relate to an industrial machinemanagement system, a method for managing an industrial machine, and anon-transitory computer-readable storage medium.

Discussion of the Background

JP 2015-087879A discloses a system that makes parameters of anindustrial machine adjustable by connecting an engineering tool to theindustrial machine, and that makes the industrial machine upload theresulting parameters to a cloud server for backup and other purposes.

SUMMARY

According to one aspect of the present invention, an industrial machinemanagement system includes circuitry that collects changeable settingdata of an industrial machine, determines, based on the setting data ateach time point of multiple time points, whether a change has been madeto the setting data, obtains change information regarding the changewhen the change is determined as having been made to the setting data,determines whether a predetermined event has occurred in the industrialmachine, identifies, when the predetermined event is determined ashaving occurred, the change information such that the change informationis related to the predetermined event, and outputs the changeinformation that is identified.

According to another aspect of the present invention, a method formanaging an industrial machine includes collecting changeable settingdata of the industrial machine, determining, based on the setting dataat each time point of multiple time points, whether a change has beenmade to the setting data, obtaining change information regarding thechange when the change is determined as having been made to the settingdata, determining whether a predetermined event has occurred in theindustrial machine, identifying, when the predetermined event isdetermined as having occurred, the change information such that thechange information is related to the predetermined event, and outputtingthe change information that is identified.

According to yet another aspect of the present invention, anon-transitory computer-readable storage medium is storing a program forcausing a computer to execute a method for managing an industrialmachine. The method includes collecting changeable setting data of theindustrial machine, determining, based on the setting data at each timepoint of multiple time points, whether a change has been made to thesetting data, obtaining change information regarding the change when thechange is determined as having been made to the setting data,determining whether a predetermined event has occurred in the industrialmachine, identifying, when the predetermined event is determined ashaving occurred, the change information such that the change informationis related to the predetermined event, and outputting the changeinformation that is identified.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the present disclosure and many of theattendant advantages thereof will be readily obtained as the samebecomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings, wherein:

FIG. 1 illustrates a general arrangement of an industrial machinemanagement system (1) according to an embodiment;

FIG. 2 illustrates an example registration screen;

FIG. 3 illustrates an example alarm list screen;

FIG. 4 illustrates an example alarm detail screen;

FIG. 5 is a functional block diagram of functions of the industrialmachine management system;

FIG. 6 illustrates an example of how data are stored in a controllerdatabase;

FIG. 7 illustrates an example of how data are stored in a relationdatabase;

FIG. 8 is a flow chart of registration processing;

FIG. 9 is a flow chart of backup processing;

FIG. 10 is a flow chart of alarm occurrence processing;

FIG. 11 is a functional block diagram of modifications of theembodiment; and

FIG. 12 illustrates an example relation database of a modification;

DESCRIPTION OF THE EMBODIMENTS 1. General Arrangement of IndustrialMachine Management System

According to the inventors' knowledge and experience, making a change tosetting data of an industrial machine, such as a program and aparameter, may cause a predetermined event such as alarming and degradedperformance in the industrial machine. It is highly laborious toidentify the piece of setting data, among a large number of pieces ofsetting data, that caused the predetermined event. In light of theconsiderations above, the inventors conducted extensive studies in anattempt to assist an analysis for what caused a predetermined event inan industrial machine, and as a result, have conceived of a novel andunique industrial machine management system and a related machine and arelated method. An industrial machine management system and a relatedmachine and a related method according to an embodiment will bedescribed in detail below.

FIG. 1 is a diagram illustrating a general arrangement of an industrialmachine management system 1 according to an embodiment. As illustratedin FIG. 1, the industrial machine management system 1 includes amanagement server 10, a robot system 20, and a user terminal 30. Themanagement server 10, the robot system 20, and the user terminal 30 areconnected to a network such as a local area network (LAN) or theInternet or another network. While FIG. 1 illustrates a singlemanagement server 10, a single robot system 20, and a single userterminal 30, these elements may be provided in plural.

The management server 10 is a server computer. It is to be noted thatthe management server 10 may be implemented by a computer such as apersonal computer, a mobile phone (including a smartphone), and aportable terminal (including a tablet terminal), if the computer hasfunctions of a server. The management server 10 includes a CPU 11, astorage 12, and a communication part 13.

The CPU 11 includes at least one processor. The storage 12 includes: avolatile memory such as RAM; and a nonvolatile memory such as a harddisc. With this configuration, the storage 12 stores various programsand data. The CPU 11 performs various kinds of processing based on theseprograms and data. The CPU 11 includes a circuit or a plurality ofcircuits (circuitry) to perform various kinds of processing based onthese programs and data. The communication part 13 includes acommunication interface such as a network card and various communicationconnectors. With this configuration, the communication part 13communicates with other apparatuses and/or devices.

The robot system 20 includes a controller 21 and a robot 22. While FIG.1 illustrates a single controller 21 and a single robot 22, theseelements may be provided in plural. For example, the robot system 20 mayinclude a plurality of controllers 21, or a single controller 21 maycontrol a plurality of robots 22.

The controller 21 is a computer that controls the robot 22. While thecontroller 21 may be a specialized controller dedicated to the robot 22,the controller 21 according to this embodiment is a general-purposecomputer. The controller 21 includes hardware such as a CPU, a RAM, ahard disc, and a communication interface. With this configuration, thecontroller 21 transmits a motion instruction to the robot 22.

The robot 22 is an industrial robot. The robot 22 may be ageneral-purpose multi-articular robot, examples including, but notlimited to, a vertical multi-articular robot, a horizontalmulti-articular robot, and a gantry robot. The robot 22 may have anynumber of arms; for example, the robot 22 may have a single arm or aplurality of arms. The robot 22 may be used in any applications,examples including, but not limited to, welding such as gas welding orarc welding, assembly of parts, and processing of food and/or foodproducts.

The controller 21 and the robot 22 are non-limiting examples of theindustrial machine recited in the appended claims. Thus, the controller21 and the robot 22 recited in this embodiment can be replaced with theindustrial machine. Any type of industrial machines are applicable tothe industrial machine management system 1, examples of the industrialmachine including, but not limited to, a motor controller, a servomotor, an inverter, a machine tool, and a Programmable Logic Controller(PLC). Any of these industrial machines may operate in the industrialmachine management system 1.

The robot system 20 may also include an apparatus or a device other thanthe controller 21 and the robot 22. A non-limiting example is a sensorthat detects a motion status in which the robot 22 is making a motion.The sensor may be any sensor such as a torque sensor, a motor encoder, aproximity sensor, a holding sensor, a pressure sensitive sensor, amotion sensor, a sputtering sensor, and a temperature sensor. The robotsystem 20 may also include: a camera that takes an image of a motion ofthe robot 22; and/or an input-output (I/O) device that receives andoutputs data.

The user terminal 30 is a computer operated by a user. In thisembodiment, the user is in charge of management of the robot system 20as a whole, and is a person different from a worker who manages thecontroller 21 and a worker who manages the robot 22. Another possibleexample is that the workers correspond to the user. Examples of the userterminal 30 include, but are not limited to, a personal computer, amobile phone (including a smartphone), and a portable terminal(including a tablet terminal).

The user terminal 30 includes a CPU 31, a storage 32, a communicationpart 33, an operation part 34, and a display 35. The CPU 31, the storage32, and the communication part 33 may be similar in hardwareconfiguration respectively to the CPU 11, the storage 12, and thecommunication part 13. The operation part 34 is an input device made upof a mouse, a keyboard, and/or a related device. Examples of the display35 include, but are not limited to, a liquid crystal display and anorganic electroluminescent (EL) display. In response to an instructionfrom the CPU 31, the display 35 displays various screens.

It is to be noted that the programs and data described as is stored inthe management server 10, the controller 21, and the user terminal 30may be supplied to these elements through the network. It is also to benoted that each of the management server 10, the controller 21, and theuser terminal 30 will not be limited to the above-described hardwareconfiguration but may have any other hardware configuration. Forexample, any of the management server 10, the controller 21, and theuser terminal 30 may include: a reader that reads a computer readableinformation storage medium (examples including an optical disc drive anda memory card slot); and/or an input/output device directly connectableto external devices (examples including a USB terminal). In this case,programs and/or data stored in an information storage medium may besupplied to the above elements through the reader and/or theinput/output device.

2. Outline of Industrial Machine Management System

In the industrial machine management system 1, the controller 21controls motions of the robot 22 based on setting data stored in thecontroller 21 itself. As used herein, the term “setting data” refers todata of settings associated with motions of the robot 22, examplesincluding, but not limited to, programs and parameters. Thus, theprograms and/or the parameters recited in this embodiment as is storedin the controller 21 may be replaced with the setting data.

A program may also be referred to as a job or a task, and encompasses aprogram code of a command (instruction) to the robot 22. In addition toa command to the robot 22, a program code may include: a variable(s)involved when the command is executed; and/or other information such asa comment, a header, and other additional notes related to the command.The programming language used in the program code may be any languageknown in the art, examples including, but not limited to, C language,C++, Java (®, registered trademark), and Python.

In one possible example, motions of the robot 22 are defined in aprogram code. For example, when the robot 22 makes motions periodically,motions of the robot 22 corresponding to the respective periods aredescribed in the program code on a time-series basis. In anotherpossible example, a track of the robot 22 is defined in a program code.The method of generating a track of the robot 22 may be any method knownin the art, examples including, but not limited to, linear interpolationand link interpolation. In the program code, time-series positions ofthe robot 22 are defined. In another possible example, a wait command tothe robot 22 is defined in a program code. The wait command shows theperiod of time for which the robot 22 waits, instead of making amovement. In another possible example, the timing and/or the strength atwhich the robot 22 opens and closes its hand is defined in a programcode. In another possible example, the output of an electric gun mountedon the robot 22 is defined in a program code.

A parameter is a value output to the robot 22, examples including, butnot limited to, the number of rotations of a motor(s) (speed), therotational angle of the motor(s), torque value, current value, and theperiod of time for which current is on. A parameter may be referred toby a program or may be described in the program. A position of the robot22 described in the program and waiting time described in the programmay be regarded as kinds of parameter. For example, individualparameters may be regarded as setting data, or a parameter file in whicha plurality of parameters are stored may be regarded as setting data. Inthe parameter file, the values of the parameter may be described on atime-series basis.

The robot system 20 is installed in a factory, a plant, or anotherindustrial facility, and a change is made to the setting data by aworker who manages the controller 21 and the robot 22 (or a worker whomanages the controller 21 and/or a worker who manages the robot 22). Asused herein, the term “change” encompasses an update, an editing, and anadjustment. In one example, the worker checks a motion that the robot 22is actually making and/or checks a state that an object (workpiece)worked on by the robot 22 is in. In this manner, the worker determineswhether it is necessary to change the setting data. In another example,the worker checks whether an alarm has occurred in the controller 21,and/or checks a stop situation of the robot 22. In this manner, theworker determines whether it is necessary to change the setting data.

When the worker determines that it is necessary to change the settingdata, the worker connects, for example, an engineering tool-equippedterminal to the controller 21, and changes the setting data. In oneexample, the worker changes a program by making an addition to,changing, or deleting a program code or by changing the value of avariable in the program. In another example, the worker prepares a newprogram and/or deletes an unnecessary program. In another example, theworker changes a program by changing the value of a parameter and/ordeleting a parameter that is no longer necessary. In another example,the worker adds a new parameter or deletes an unnecessary parameter.

Making a change to the setting data may cause the controller 21 and therobot 22 to operate differently, and this may cause a predeterminedevent to occur. In light of this, this embodiment makes the user specifyin advance setting data related to a predetermined event; and when thepredetermined event occurs, displays information regarding a change madeto the setting data specified by the user.

As used herein, the term “predetermined event” is intended to mean anyevent specified in advance. Examples of the event include, but are notlimited to, an occurrence of an alarm, degradation of performance of thecontroller 21 or the robot 22, contact or interference between therobots 22, an event in which the motion status of the controller 21 orthe robot 22 falls outside a reference range, and an event in which aparticular switch is turned on. Examples of the motion status of thecontroller 21 or the robot 22 include, but are not limited to, awaveform of a torque signal, maximum torque amount, a convergence valueof the torque signal, the rising timing of the torque signal, theconvergence timing of the torque signal, position information regardingthe position of a motor, speed information regarding the speed of themotor, the amount of overshoot, settling time, tact time, cycle time,CPU usage, memory usage, and communication traffic.

As used herein, the phrase “setting data related to an event” isintended to mean a piece of setting data that may possibly have causedthe event to occur. In other words, setting data related to an event isa piece of setting data that should be output when the event occurs.This embodiment is regarding a case where setting data related to anevent is a piece of setting data regarded and specified by the user asbeing related to the event. That is, this embodiment is regarding a casewhere the user manually specifies setting data related to an event. Itis to be noted, however, that setting data related to an event may beautomatically specified based on a statistical analysis of a change madeto setting data in relation to an occurrence of an alarm, as inmodification 1 described later.

In this embodiment, an alarm will be described as an example event.Thus, the term “alarm” used in this embodiment can be replaced with“event”. For example, when the user operates the user terminal 30 toaccess the management server 10, the display 35 displays a registrationscreen for registering setting data related to an alarm. While in thisembodiment setting data related to an alarm is registered on anindividual controller 21 basis, setting data related to an alarm may becommon to the plurality of controllers 21.

FIG. 2 illustrates an example registration screen G1. As illustrated inFIG. 2, a name of a registration target controller 21 is displayed onthe registration screen G1. The registration target controller 21 may beany controller 21; for example, the user specifies the registrationtarget controller 21 before the registration target controller 21 isdisplayed on the registration screen G1. In the example illustrated inFIG. 2, it is “Controller X” in which setting data related to alarms areregistered.

Thus, the user is able to select any piece of setting data stored in theregistration target controller 21 and specify the piece of setting dataas setting data related to an alarm. In this embodiment, alarms areclassified by alarm codes, and a piece of setting data related to analarm denoted by a corresponding alarm code is registered. It is to benoted that any number of setting data may be registered in relation toalarms and that the setting data may not necessarily be registered inrelation to all alarms.

On the registration screen G1, the alarm denoted by alarm code “001” istorque abnormality, and setting data registered in relation to the alarmare “Program A” and “Parameter B”. Also on the registration screen G1,the alarm denoted by alarm code “002” is temperature abnormality, and nosetting data related to the alarm is registered yet. Also on theregistration screen G1, the alarm denoted by alarm code “003” is speedabnormality, and setting data registered in relation to the alarm is“Program C”. Thus, the registration screen G1 displays a list ofregistered setting data related to alarms denoted by alarm codes.

When the user has selected pull-down menu M10, M11, or M12, a list ofsetting data stored in the corresponding controller 21 appears. From thelist, the user specifies a piece of setting data related to the alarm,thus registering the piece of setting data. It is to be noted that theuser may not necessarily specify all pieces of setting data related toalarms; the setting data may be registered by default. It is also to benoted that the registration screen G1 may be adapted such that the useris able to cancel registration of a piece of setting data related to analarm.

Registering setting data in relation to an alarm on the registrationscreen G1 ensures that when the alarm occurs, a change made to thesetting data related to the alarm is displayed. For example, when analarm occurs in the robot system 20, a notification such as anelectronic mail is transmitted to the user terminal 30. In response tothe notification, the user operates the user terminal 30 to access themanagement server 10, thereby causing the display 35 to display an alarmlist screen on which a list of alarms that occurred are shown.

FIG. 3 illustrates an example alarm list screen G2. As illustrated inFIG. 3, the alarm list screen G2 displays names of controllers 21 inwhich alarms have occurred, dates and times of alarm occurrences, alarmcodes, and alarm names. The alarm list screen G2 may display all or someof the alarms that occurred in the past.

When the user has selected an alarm displayed on the alarm list screenG2, the display 35 displays an alarm detail screen, which shows detailsof the alarm. The following description will focus on a case where theuser has selected the alarm of “003”, which occurred in “Controller X”at 10:25:08 on Jan. 16, 2019.

FIG. 4 illustrates an example alarm detail screen. As illustrated inFIG. 4, alarm detail screen G3 displays information regarding changesmade to setting data related to the alarm of “003”, which occurred in“Controller X”. In the example illustrated in FIG. 4, “Program C” isregistered as setting data related to the alarm of “003”, and the alarmdetail screen G3 displays the name of the program and content of thechanges.

For example, the content of the changes is displayed in the form of acomparison between program codes of “Program C” at the alarm occurrencetime and program codes of “Program C” before the alarm occurrence time.In the example illustrated in FIG. 4, “Program C” was changed on Jan.11, 2019, and the alarm detail screen G3 displays: the latest version ofthe program codes at the time at which the alarm occurred (program codesobtained as a backup on Jan. 15, 2019, which is the day before the alarmoccurred); and a previous version of the program codes obtained on Jan.10, 2019, which is before the changes (that is, program codes oneversion previous to the latest version). It is to be noted that theprevious version of the program codes that can be displayed on the alarmdetail screen G3 may be two or more versions previous to the latestversion, or that a plurality of previous versions may be displayed onthe alarm detail screen G3 (for example, one version previous to thelatest version and two versions previous to the latest version).

In this embodiment, the content of the changes made to the setting datais emphasized on the alarm detail screen G3. In the example illustratedin FIG. 4, the content of the changes is emphasized using underlines,showing that the movement command “MOVJ C00001 VJ=80.00” to the robot 22and the movement command “MOVJ C00002 VJ=80.00” to the robot 22 arechanged.

It is to be noted that the method of emphasizing the detail of thechange will not be limited to the use of underlines, and any othermethod may be used. A possible example is to use a predetermined color,such as red and blue, to emphasize the detail of the change made to thesetting data. Another possible example is to make the detail of thechange larger in font size than the other elements of the setting data.Another possible example is to show the detail of the change in Italicor bold. Another possible example is to show the detail of the changeusing a particular font different from the other elements of the settingdata.

By checking the alarm detail screen G3, the user estimates that thechanges made to the movement commands may have caused the alarm of“003”. It is to be noted, however, that the content displayed on thealarm detail screen G3 only indicates a possibility of what caused thealarm, and may not necessarily show that the content actually caused thealarm. Under the circumstances, the user considers other possiblefactors comprehensively and performs an analysis for what caused thealarm.

It is to be noted that when a parameter is registered as setting datarelated to an alarm, the alarm detail screen G3 displays a name of theregistered parameter and content of a change(s) made to the parameter.In one example, the content of the change to be shown may be the amountby which the parameter was changed. In another example, when a parameterselected includes values aligned on a time-series basis, the content ofthe change may be the time point at which the parameter was changed. Inanother example, when a parameter file selected stores a plurality ofparameters, the content of the change may be a parameter, among theplurality of parameters, that was changed.

Thus, the industrial machine management system 1 according to thisembodiment registers in advance pieces of setting data related toalarms. When an alarm occurs in a controller 21, the alarm detail screenG3 displays name and change content associated with a piece of settingdata related to the alarm. In this manner, the industrial machinemanagement system 1 assists an analysis for what caused an alarm in anindustrial machine. The industrial machine management system 1 accordingto this embodiment will be described in more detail below.

3. Functions of Industrial Machine Management System

FIG. 5 is a functional block diagram of functions of the industrialmachine management system 1. The following description is regardingfunctions of the controller 21 and functions of the management server10.

Functions of Controller

As illustrated in FIG. 5, the controller 21 includes a data storage 200.The data storage 200 is mainly implemented by the storage of thecontroller 21, and stores at least one setting data. It is to be notedthat the number of setting data stored in the data storage 200 may beany number that is determined based on the purpose and application ofthe controller 21 and the robot 22. For example, when the controller 21controls a plurality of robots 22, the data storage 200 stores settingdata on an individual robot 22 basis.

The setting data stored in the data storage 200 may be changed by theworker operating the worker's terminal or by the user operating the userterminal 30. In this embodiment, a backup of the setting data isobtained periodically. Specifically, the management server 10 transmitsa transmission command for the setting data to the controller 21, and inresponse, the controller 21 transmits the setting data stored in thedata storage 200 to the management server 10. It is to be noted that thecontroller 21 may voluntarily transmit the setting data to themanagement server 10.

The data storage 200 stores alarm occurrence conditions. In thisembodiment, the data storage 200 stores an alarm occurrence condition onan individual alarm code basis. An alarm occurrence condition may be anycondition related to a motion status of the controller 21 or the robot22. The method of detecting an alarm may be any method known in the art.For example, the controller 21 obtains a motion status of the robot 22based on a detection signal detected by the sensor, and determineswhether an alarm occurrence condition is met.

In one example, for an alarm related to torque abnormality, thecontroller 21 determines that the alarm occurrence condition is met whenthe peak value of a torque signal, the convergence value of the torquesignal, the rising timing of the torque signal, or the convergencetiming of the torque signal falls outside a reference range. In anotherexample, for an alarm related to temperature abnormality, the controller21 determines that the alarm occurrence condition is met when the valueof temperature received from the temperature sensor falls outside areference range. In another example, for an alarm related to speedabnormality, the controller 21 determines that the alarm occurrencecondition is met when the value of speed received from the motor encoderor the motion sensor falls outside a reference range. Thus, thecontroller 21 determines whether an alarm occurrence condition is metbased on information received from a sensor or based on a motion statusof the controller 21.

When the controller 21 determines that any alarm occurrence condition ismet, the controller 21 transmits an alarm occurrence notification to themanagement server 10. The alarm occurrence notification includes: thedate and time of occurrence of the alarm; and the alarm code made to berelated to the alarm occurrence condition. The date and time ofoccurrence of the alarm may be present date and time obtained from, forexample, a real-time clock or a GPS signal. While this embodiment isregarding a case where the controller 21 determines whether an alarm hasoccurred, the management server 10 or another computer may determinewhether an alarm has occurred.

Functions of Management Server

As illustrated in FIG. 5, the management server 10 includes a datastorage 100, a registration part 101, a collection part 102, a changedetermination part 103, an obtaining part 104, an event determinationpart 105, an identifying part 106, and an outputting part 107. The datastorage 100 is mainly implemented by the storage 12, and the otherfunctions are mainly implemented by the CPU 11.

Data Storage

The data storage 100 stores data for managing the robot system 20. Thedata storage 100 stores a controller database DB1 and a relationdatabase DB2. The controller database DB1 stores data regarding thecontrollers 21, and the relation database DB2 stores setting dataregistered in relation to alarms.

FIG. 6 illustrates an example of how data is stored in the controllerdatabase DB1. As illustrated in FIG. 6, the controller database DB1stores names of the controllers 21, backup information, and occurringalarm information. It is to be noted that the information stored in thecontroller database DB1 will not be limited to the above-describedinformation. For example, the controller database DB1 may store names ofproduction lines to which the controllers 21 belong and/or trace datashowing motion statuses of the robot 22 on a time-series basis. As usedherein, the term “production line” refers to a work group in a facility.Controllers 21 belonging to an identical production line performmachining or processing, in turn, on objects conveyed by a conveyancedevice such as a belt conveyor. It will be assumed that information thata controller 21 belongs to a production line is defined in a database ofthe controller 21.

The backup information is information regarding backup of the settingdata. Examples of the backup information include, but are not limitedto, backup time of the setting data, real data of the setting data fromwhich a backup was obtained, and changed-unchanged information regardingwhether a change is made to the setting data. It is to be noted that thebackup time of the setting data may be not only date but also time.

In this embodiment, the setting data stored in the controller databaseDB1 is setting data that is collected by the collection part 102,described later. In light of this, the data storage 100 stores, as abackup, the setting data collected by the collection part 102. Since abackup of the setting data is obtained repeatedly, the controllerdatabase DB1 stores a backup history of the setting data obtained in thepast.

It is to be noted that old setting data may be automatically deleted sothat only setting data corresponding to a predetermined recent period oftime is stored or setting data corresponding to an n-th backup (n isnatural number) is stored. In this embodiment, the setting data of allthe controllers 21 are subjected to backup. Another possible example isthat the setting data of some of the controllers 21 is subjected tobackup. In this case, the determination as to whether a change has beenmade may be performed with respect to only those setting data that aresubjected to backup.

When a change is made to the setting data, the changed-unchangedinformation shows a first value (a value corresponding to “change made”in FIG. 6). When no change is made to the setting data, thechanged-unchanged information shows a second value (a valuecorresponding to “no change” in FIG. 6). Thus, the first value of thechanged-unchanged information shows that a change in the setting data isdetected at the corresponding backup time, while the second value of thechanged-unchanged information shows that no change in the setting datais detected at the corresponding backup time. In the changed-unchangedinformation with the first value, a name(s) of the setting data that ischanged is stored.

The occurring alarm information is information regarding an alarm thatoccurred in the controller 21. For example, the occurring alarminformation stores: the date and time of occurrence of the alarm; andthe alarm code of the alarm. In this embodiment, when an alarm occurs,the controller 21 transmits an alarm occurrence notification to themanagement server 10. Upon receipt of the alarm occurrence notification,the management server 10 obtains, from the alarm occurrencenotification, the date and time of occurrence of the alarm and the alarmcode of the alarm. Then, the management server 10 regards the date andtime and the alarm code as occurring alarm information, and stores theoccurring alarm information in the controller database DB1. It will beassumed that alarm codes in relation to alarm names are defined inadvance in another database. The alarm name may not necessarily beincluded in the occurring alarm information.

FIG. 7 illustrates an example of how data are stored in the relationdatabase DB2. As illustrated in FIG. 7, the relation database DB2stores, on an individual controller 21 basis, alarm codes registered inrelation to the setting data. The relation database DB2 may be common toall users or may show different registrations from user to user. Forexample, one user may register “Program A” and “Parameter B” in relationto the alarm of “001”, while another user may register “Program C” inrelation to the alarm of “001”.

It is to be noted that the data stored in the data storage 100 will notbe limited to the above-described data. In one example, the data storage100 may store a database in which basic information of the user and theworker is stored. In another example, the data storage 100 may storedata (for example, HTML data and/or image data) to be displayed on theregistration screen G1, the alarm list screen G2, and the alarm detailscreen G3.

Register

The registration part 101 registers, on an individual alarm code basis,kinds of setting data specified by the user. As used herein, the phrase“to register” refers to storing a kind of setting data (setting datakind) in the data storage 100; in this embodiment, the phrase refers tostoring a setting data kind in the relation database DB2. While thisembodiment is regarding a case where a setting data kind is registeredon an individual alarm code basis, a setting data kind may notnecessarily be registered on an individual alarm code basis. That is, asetting data kind common to a plurality of alarm codes may be registeredas related setting data.

In this embodiment, since an alarm is equivalent to an event, an alarmcode is equivalent to an event kind. Names of event kinds vary fromevent to event, and an alarm name may be regarded as being equivalent toan event. In another example, when degradation of performance isequivalent to an event, the kind of the performance degraded may beequivalent to an event kind. Examples of the event kind include, but arenot limited to, shortened service life, shortened tact time, anddegradation in quality of the object worked on.

In another example, when falling of a motion status outside a referencerange is equivalent to an event, the kind of the motion status fallingoutside the reference range may be equivalent to an event kind. Inanother example, when the following items fall outside respectivereference ranges, each falling may be equivalent to an event kind: thewaveform of a torque signal, maximum torque, a convergence value of atorque signal, the rising timing of the torque signal, the convergencetiming the torque signal, position information regarding the position ofa motor, speed information regarding the speed of the motor, the amountof overshoot, settling time, tact time, cycle time, CPU usage, memoryusage, and communication traffic.

In this embodiment, the user specifies on the registration screen G1setting data related to alarms. Then, the registration part 101registers, in the relation database DB2, the setting data specified bythe user. Specifically, the registration part 101 relates an alarm codewith a kind of setting data specified on pull-down menu M10, M11, orM12, and stores the resulting relation in the relation database DB2.More specifically, the registration part 101 receives from the userterminal 30 a combination of an alarm code and a setting data kindspecified by the user, and stores the combination in the relationdatabase DB2.

Collection Part

The collection part 102 collects changeable setting data from thecontroller 21. As used herein, the term “to collect” refers to obtain orreceive data from the controller 21. The collection part 102 collectsthe setting data at each time point of a plurality of time points. Inother words, the collection part 102 repeatedly collects the settingdata. The collection part 102 may collect the setting data periodicallyor non-periodically. A possible example of when the collection part 102collects the setting data non-periodically is that when an alarm occurs.Another possible example is when the user instructs collection of thesetting data.

This embodiment is regarding a case where the controller 21 uploads thesetting data at a demand from the management server 10, instead ofuploading the setting data voluntarily. In response to the demand fromthe management server 10, the collection part 102 makes a demand to thecontroller 21 for the setting data. In response to the demand, thecontroller 21 transmits the setting data to the collection part 102. Inthis manner, the collection part 102 collects the setting data. When therobot system 20 includes a plurality of controllers 21, the collectionpart 102 collects the setting data from each of the plurality ofcontrollers 21.

The collection part 102 collects the setting data when a predeterminedcondition is met. The predetermined condition may be any conditionspecified for collection of the setting data. In this embodiment, onepredetermined condition is that backup time has come. Another possibleexample is that an alarm occurs in the controller 21. Another possibleexample is that trace data of a torque signal associated with the robot22 has turned into a predetermined state. Another possible example isthat the user or the worker has made a command for a backup.

The backup time may be stored in advance in the data storage 100, andany point of time may be set as the backup time. In one example, thebackup time may be the same point of time daily or may vary from week toweek. It is to be noted that a backup may not necessarily be obtaineddaily; for example, a backup may be scheduled to be obtained at timeintervals of a few to several days or may be scheduled to be obtained inbusiness days on which the factor operates.

The collection part 102 obtains knowledge of the present date and timeusing a real-time clock, a GPS signal, or similar means, and determineswhether predetermined backup time has come. When the collection part 102determines that the predetermined backup time has come, the collectionpart 102 makes a demand to the controller 21 for the setting data. It isto be noted that the backup time may be set to be common to all thecontrollers 21 or may be set to vary from controller 21 to controller21. Upon collecting the setting data from the controller 21, thecollection part 102 stores the setting data in the controller databaseDB as a backup.

Change Determination Part

Based on the setting data at each time point of the plurality of timepoints, the change determination part 103 determines whether a changehas been made to the setting data. Specifically, the changedetermination part 103 compares the setting data collected at a firsttime point with the setting data collected at a second time pointdifferent from the first time point. Based on the comparison, the changedetermination part 103 determines whether a change has been made to thesetting data. In other words, when the setting data is collected by thecollection part 101, the change determination part 103 compares thecollected setting data with the setting data collected at an earlierpoint of time. Based on the comparison, the change determination part103 determines whether a change has been made to the setting data. Whenthe change determination part 103 determines that a change is made tothe setting data, the change determination part 103 stores a first valueand the name of the changed setting data in the changed-unchangedinformation. When the change determination part 103 determines that nochange is made to the setting data, the change determination part 103stores a second value in the changed-unchanged information.

This embodiment is regarding a case where the setting data is determinedas being changed regardless of whether the change made to the settingdata is a major or minor change (that is, the setting data is determinedas being changed even if the setting data is changed only partially). Inone example, when the latest program code and the previous program codematch completely, the change determination part 103 determines that noprogram change has been made, while when the latest program code and theprevious program code do not match completely, the change determinationpart 103 determines that a program change has been made. In anotherexample, when a new program is added to the setting data or an existingprogram in the setting data is deleted, the change determination part103 determines that a program change has been made. In another example,when the latest parameter value(s) and the previous parameter value(s)match completely, the change determination part 103 determines that noparameter change has been made, while when the latest parameter value(s)and the previous parameter value(s) do not match completely, the changedetermination part 103 determines that a parameter change has been made.In another example, when a new parameter is added to the setting data oran existing parameter in the setting data is deleted, the changedetermination part 103 determines that a parameter change has been made.

It is to be noted that it is possible to determine that no change hasbeen made to the setting data when a predetermined change is not made tothe setting data. Examples of the predetermined change include a changemade to a particular command in a program (such as a movement commandand a wait command), and a change made to a particular parameter (suchas output torque and motor speed). Other examples of the predeterminedchange include a situation in which the amount by which a variable in aprogram changed is equal to or higher than a threshold, and a situationin which the amount by which a parameter changed is equal to or higherthan a threshold.

In this embodiment, the change determination part 103 determines, atevery backup time, whether a change has been made to the setting data.For this purpose, the change determination part 103 includes a backupdetermination part 103A. The backup determination part 103A determines,based on setting data collected for backup purposes, whether a changehas been made to the setting data. Specifically, when the collectionpart 102 has collected backup target setting data, the backupdetermination part 103A compares the backup target setting data withbackup target setting data obtained at an earlier point of time, andbased on the comparison, determines whether a change has been made tothe setting data. It is to be noted that the backup determination part103A may perform the above determination after the setting data isstored into the controller database DB1 (that is, after a backup iscompleted), or may perform the above determination after before thesetting data is stored into the controller database DB1 (that is, beforea backup is completed).

Obtaining Part

When the change determination part 103 determines that a change is madeto the setting data, the obtaining part 104 outputs change information.The change information is regarding the change made to the setting data.The change information may be any information insofar as the informationis regarding the change made to the setting data. Examples of the changeinformation include, but are not limited to: change detail information,which is regarding a detail of the change made to the setting data; andchange kind information, which is regarding a kind of the setting datato which the change is made. Other examples of the change informationinclude: the point of time at which the change was made to the settingdata; the fact that the change is made to the setting data; the personwho made the change to the setting data; the controller 21 whose settingdata is changed; and the robot 22 that operates based on the changedsetting data.

In this embodiment, the change content information is displayed on thealarm detail screen G3. For this purpose, the obtaining part 104includes a content obtaining part 104A. The content obtaining part 104Aobtains the change content information. When the change determinationpart 103 determines that a change is made to the setting data, thecontent obtaining part 104A obtains, as the change information, changecontent information regarding content of the change made to the settingdata. Specifically, the content obtaining part 104A obtains the changecontent information based on pre-change setting data and post-changesetting data. After obtaining the change content information, thecontent obtaining part 104A may store the change content information inthe controller database DB1.

The change detail information is information regarding a detail of thechange made to the setting data. The detail of the change may be aposition on the setting data to which the change was made, or may be apart of the setting data to which the change was made. In one example,when a change is made to a program, the change detail informationdenotes a program code that has been added, changed, or deleted. Inanother example, when a change is made to a parameter, the change detailinformation denotes the amount of the change made to the parameter. Itis to be noted that when the setting data is a parameter file in which aplurality of parameters are stored, the change detail information maydenote the parameter in the parameter file to which the change is made.In one example, when a plurality of kinds of parameters are stored in aparameter file, the change detail information may denote the kind of theparameter in the parameter file to which the change is made. In anotherexample, when values of a parameter are stored in time order in aparameter file, the change detail information may denote the point oftime in the parameter file at which the change was made to theparameter.

Also in this embodiment, the change kind information is displayed on thealarm detail screen G3. For this purpose, the obtaining part 104includes a change kind obtaining part 104B. The change kind obtainingpart 104B obtains the change kind information. In the controller 21, aplurality of kinds of setting data are changeable. When the changedetermination part 103 determines that a change is made to the settingdata, the change kind obtaining part 104B obtains, as the changeinformation, change kind information regarding the kind of the settingdata to which the change is made. After obtaining the change kindinformation, the change kind obtaining part 104B may store the changekind information in the controller database DB1.

The change kind information is information regarding the kind of thesetting data to which a change is made. In one example, when a change ismade to a program, the change kind information denotes the name of theprogram (file name of the program) to which the changed is made. Inanother example, when a change is made to a parameter, the change kindinformation denotes the name of the parameter (file name of theparameter) to which the changed is made. It is to be noted that thekind(s) of the setting data may be identified by other identificationinformation such as ID.

Event Determination Part

The event determination part 105 determines whether a predeterminedevent has occurred in the controller 21. Specifically, the controller 21first determines whether an event has occurred in the controller 21, andwhen the event occurs, the controller 21 transmits a predeterminednotification to the event determination part 105. Thus, the eventdetermination part 105 determines whether the predetermined notificationhas been received from the controller 21. It is to be noted that thecontroller 21 may not necessarily determine whether an event hasoccurred in the controller 21; in this case, the event determinationpart 105 may receive a motion status of the controller 21 or the robot22, and determine whether the motion status meets an occurrencecondition for the event.

In this embodiment, an alarm is equivalent to an event. For this reason,the event determination part 105 includes an alarm determination part105A. The alarm determination part 105A determines whether an alarm hasoccurred as an event in the controller 21. Specifically, when an alarmoccurs, the controller 21 transmits to the management server 10 an alarmoccurrence notification including the date and time of occurrence of thealarm and the alarm code. Then, the alarm determination part 105Adetermines whether the alarm has occurred by determining whether thealarm occurrence notification has been received. When the alarmoccurrence notification is received, the alarm determination part 105Adetermines that the alarm occurs. When no alarm occurrence notificationis received, the alarm determination part 105A determines that no alarmoccurs.

While this embodiment is regarding a case where the controller 21determines whether the alarm occurrence condition is met, it is possiblefor the management server 10 to receive from the controller 21 a motionstatus of the controller 21 or the robot 22 and for the alarmdetermination part 105A to determine, based on the motion status that isreceived, whether the alarm occurrence condition is met. In this case,when the alarm determination part 105A determines that the alarmoccurrence condition is met, the alarm determination part 105Adetermines that the alarm occurs. When the alarm determination part 105Adetermines that the alarm occurrence condition is not met, the alarmdetermination part 105A determines that no alarm occurs.

When degradation of performance is equivalent to an event, the eventdetermination part 105 receives information regarding performance fromthe controller 21, and determines whether the performance indicated bythe information is outside a reference range. Examples of theinformation regarding performance include, but are not limited to,lifetime, load ratio, and tact time associated with a component of therobot 22. The determination as to degradation of performance may be madeon the side of the controller 21, and the event determination part 105may only receive the determination made by the controller 21.

When a situation in which a motion status falls outside a referencerange is equivalent to an event, the event determination part 105receives information regarding the motion status from the controller 21,and determines whether the motion status indicated by the information isoutside a reference range. Examples of the information regarding amotion status include, but are not limited to: trace data, which showsinformation on a time-series basis; and information as of a point oftime, such as a torque signal value and a speed value. The determinationas to whether a motion status is outside a reference range may be madeon the side of the controller 21, and the event determination part 105may only receive the determination made by the controller 21.

Identifying Part

When the event determination part 105 determines that an event occurs,the identifying part 106 identifies change information related to theevent. In this embodiment, since the relation database DB2 shows eventsin relation to setting data, the identifying part 106 identifies, fromthe relation database DB2, change information regarding a piece ofsetting data made to be related to the event that occurs. For example,from change information obtained in the past, the identifying part 106identifies change information closest to the time at which the eventoccurred.

The identifying part 106 may identify one piece of change informationclosest to the time at which the event occurred, or may identify apredetermined number of pieces of change information arranged indecreasing order of closeness to the time at which the event occurred.That is, the identifying part 106 may identify any number of pieces ofchange information. Specifically, the identifying part 106 may identifyone piece of change information (as in this embodiment) or may identifytwo, three, four, or more pieces of change information.

The change information identified by the identifying part 106 is suchchange information that should be output by the outputting part 107among change information obtained in the past. Under the circumstances,the identifying part 106 narrows down the change information obtained inthe past to change information that should be output by the outputtingpart 107. In other words, from change information of setting data thatwere changed within a period of time starting from the time at which theevent occurred point, the identifying part 106 extracts changeinformation that should be output by the outputting part 107.

In this embodiment, the identifying part 106 identifies changeinformation regarding setting data related to an alarm, and does notidentify change information regarding setting data unrelated to thealarm. If, therefore, the time at which setting data unrelated to analarm was changed is closer to the time at which an alarm occurred thanthe time at which setting data related to an alarm was changed is to thetime at which the alarm occurred, the identifying part 106 does notidentify the change information regarding setting data unrelated to thealarm but identifies the change information regarding setting datarelated to the alarm.

In the data storage examples illustrated in FIGS. 6 and 7, the alarm of“003” occurred in “Controller X” at 10:25:08 on Jan. 16, 2019. Settingdata changes that were made at time closest to the time at which thealarm of “003” occurred are changes to “Program A” and “Parameter B”,which were detected at backup time of Jan. 15, 2019. The setting data“Program A” and “Parameter B”, however, are unrelated to the alarm andthus are not identified by the identifying part 106. Instead, theidentifying part 106 identifies change information regarding “ProgramC”, which was detected at backup time of Jan. 11, 2019.

In this embodiment, the change content information is displayed on thealarm detail screen G3. For this purpose, the identifying part 106includes a content identifying part 106A. The content identifying part106A identifies the change content information. When the eventdetermination part 105 determines that an event occurs, the contentidentifying part 106A identifies change content information related tothe event. For example, from change content information obtained in thepast, the content identifying part 106A identifies change contentinformation closest to the time at which the event occurred. The contentidentifying part 106A identifies a predetermined number of pieces ofchange content information arranged in decreasing order of closeness tothe time at which the event occurred. The content identifying part 106Aidentifies change content information regarding setting data related tothe event, and does not identify change content information regardingsetting data unrelated to the event.

In this embodiment, the change kind information is displayed on thealarm detail screen G3. For this purpose, the identifying part 106includes a change kind identifying part 106B. The change kindidentifying part 106B identifies the change kind information. When theevent determination part 105 determines that an event occurs, the changekind identifying part 106B identifies change kind information related tothe event. For example, from change kind information obtained in thepast, the change kind identifying part 106B identifies change kindinformation closest to the time at which the event occurred. The changekind identifying part 106B identifies a predetermined number of piecesof change kind information arranged in decreasing order of closeness tothe time at which the event occurred. The change kind identifying part106B identifies change kind information regarding setting data relatedto the event, and does not identify change kind information regardingsetting data unrelated to the event.

In this embodiment, an alarm is equivalent to an event. For this reason,the identifying part 106 includes an alarm relation identifying part106C. When the alarm determination part 105A has determined whether analarm has occurred, the relation identifying part 106C identifies changeinformation related to the alarm. In this embodiment, since the relationdatabase DB2 shows alarms in relation to setting data, the alarmrelation identifying part 1060 identifies, from the relation databaseDB2, change information regarding a piece of setting data made to berelated to the alarm that occurs. For example, from change informationobtained in the past, the alarm relation identifying part 106Cidentifies change information closest to the time at which the alarmoccurred. The alarm relation identifying part 106 identifies apredetermined number of pieces of change information arranged indecreasing order of closeness to the time at which the alarm occurred.The alarm relation identifying part 106C identifies change informationregarding setting data related to the alarm, and does not identifychange information regarding setting data unrelated to the alarm.

In this embodiment, a plurality of kinds of setting data are changeablein the controller 21, and a plurality of kinds of events are occurrablein the controller 21. For this reason, the identifying part 106 includesa related kind identifying part 106D. When one kind of event among aplurality of kinds of events is determined as occurring, the relatedkind identifying part 106D identifies change information of a kind ofsetting data related to the one kind of event. In this embodiment, sincethe relation database DB2 shows event kinds in relation to setting data,the related kind identifying part 106D identifies, from the relationdatabase DB2, change information of setting data made to be related tothe kind of event that occurs, and does not identify change informationof setting data that is not made to be related to the kind of event thatoccurred.

In this embodiment, a kind of setting data related to a kind of event isregistered by the user. For this reason, the identifying part 106includes a registered kind identifying part 106E. When the kind ofevent, among the plurality of kinds of events, is determined asoccurring, the registered kind identifying part 106E identifies, basedon the registered content registered by the registration part 101,change information of the kind of setting data related to the kind ofevent. Since the kind of setting data registered by the registrationpart 101 is specified by the user, the registered kind identifying part106E identifies change information of the kind of setting data specifiedby the user, and does not identify change information of a kind ofsetting data that is not specified by the user.

Outputting Part

The outputting part 107 outputs the change information identified by theidentifying part 106. While this embodiment is regarding a case wherethe change information output onto screen in a visually recognizablemanner, the change information may be output in the form of sound ordata (file output). When the change information is output in the form ofdata output, the change information is output to and recorded in anexternal device or a memory in the form of data. In this case, thechange information may be output in any data form, examples including,but not limited to, image form, text form, document form, tabular form,csv form, and message form. Another possible example that a messageincluding the change information may be sent, which may be regarded asan output of the change information.

In this embodiment, the change content information is displayed on thealarm detail screen G3. For this purpose, the outputting part 107includes a content outputting part 107A. The content outputting part107A outputs the change content information identified by the contentidentifying part 106A. Specifically, the content outputting part 107Aoutputs the change content information such that the change contentinformation shows a difference between setting data. While thisembodiment is regarding a case where all of the difference is obtainedas the change content information, only part of the difference may beobtained as the change content information.

In one example, the content outputting part 107A outputs the changecontent information such that the change content information shows adiscrepancy between a character string of a program code of a pre-changeprogram and a character string of a program code of a post-changeprogram. In another example, the content outputting part 107A outputsthe change content information such that the change content informationshows a difference between a pre-change parameter value and apost-change parameter value. In this embodiment, the content outputtingpart 107A displays, on the alarm detail screen G3, content of a changemade to a program code and/or content of a change made to a parameter.

Also in this embodiment, the change kind information is displayed on thealarm detail screen G3. For this purpose, the outputting part 107includes a kind outputting part 107B. The kind outputting part 107Boutputs the change kind information identified by the change kindidentifying part 106B. The change determination part 103 is capable ofdetermining, on an individual setting data kind basis, whether a changehas been made to the setting data. When the change determination part103 makes such determination, the kind outputting part 107B outputs thechange kind information such that the change kind information denotesthe kind of the setting data that the change determination part 103determines as being changed. For example, the kind outputting part 107Boutputs, as the change kind information, the name of a program that thechange determination part 103 determines as being changed. In thisembodiment, the kind outputting part 107B displays, on the alarm detailscreen G3, the name of the program that is changed.

4. Processings Performed in Industrial Machine Management System

Processings performed in the industrial machine management system 1 willbe described. The following description is regarding registrationprocessing for registering related setting data, backup processing ofobtaining a backup of setting data, and alarm occurrence processingperformed when an alarm occurs. These processings are exampleprocessings performed by the functional blocks illustrated in FIG. 5.

Registration Processing

FIG. 8 is a flow chart of the registration processing. The screendisplay processing illustrated in FIG. 8 is performed by: the CPU 11 ofthe management server 10 when the CPU 11 operates according to a programstored in the storage 12; and the CPU 31 of the user terminal 30 whenCPU 31 operates according to a program stored in the storage 32.

As illustrated in FIG. 8, the CPU 31 of the user terminal 30 transmitsto the management server 10 a demand for displaying the registrationscreen G1 (S100). The demand for displaying the registration screen G1may be made by transmitting predetermined form data. In one example,when the registration screen G1 is displayed on a web browser, thedemand may contain a universal resource locator (URL). In anotherexample, when the registration screen G1 is displayed on an application,the demand may contain identification information of the registrationscreen G1. The same applies in the demands for displaying the otherscreens, described later. It will be assumed that the demand fordisplaying transmitted at S100 includes the name of the registrationtarget controller 21.

Upon receipt of the demand for displaying the registration screen G1,the CPU 11 of the management server 10 generates, based on thecontroller database DB1 and the relation database DB2, data to bedisplayed on the registration screen G1, and transmits the data to theuser terminal 30 (S101). At S101, the CPU 11 refers to the backupinformation stored in the controller database DB1 and identifies kindsof the setting data stored in the registration target controller 21.Then, the CPU 11 sets the kinds of setting data to be shown on pull-downmenus M10 to M12. Then, the CPU 11 refers to the relation database DB2and identifies relationships between alarm codes and related settingdata, and determines items to be displayed on the registration screenG1. The items are alarm code, alarm name, and kinds of setting dataregistered at the present time.

Upon receipt of the data to be displayed on the registration screen G1,the CPU 31 of the user terminal 30 causes the display 35 to display theregistration screen G1 based on the data that is received (S102). TheCPU 31 receives a detection signal from the operation part 34 and, basedon the detection signal, identifies the user's manipulation of theoperation part 34 (S103). It will be assumed that the manipulation atS103 is either registration manipulation of registering related settingdata or cancellation manipulation of canceling registered setting data.

When the manipulation at S103 is registration manipulation ofregistering related setting data (S103: registration manipulation), theCPU 31 transmits a registration demand for registration of relatedsetting data (S104). The registration demand may be made by transmittinga predetermined form of data, and includes, for example, an alarm codeand a setting data name specified by the user.

Upon receipt of the registration demand, the CPU 11 of the managementserver 10 registers the setting data specified by the user as settingdata related to the alarm having the alarm code specified by the user(S105), thus ending this processing. At S105, the CPU 11 mutuallyrelates the alarm code and the setting data included in the registrationdemand, and stores the alarm code and the setting data in the relationdatabase DB2.

When the manipulation at S103 is cancellation manipulation of cancelingrelated setting data (S103: cancellation manipulation), the CPU 31transmits a cancellation demand for canceling, from the alarm code,related setting data specified by the user (S106). The cancellationdemand may be made by transmitting a predetermined form of data, andincludes, for example, an alarm code and a setting data name specifiedby the user.

Upon receipt of the cancellation demand, the CPU 11 of the managementserver 10 cancels the setting data specified by the user from the alarmhaving the alarm code specified by the user (S107), thus ending thisprocessing. At S107, the CPU 11 updates the relation database DB2 suchthat the relation between the alarm code and the setting data includedin the cancellation demand is canceled.

Backup Processing

FIG. 9 is a flow chart of the backup processing performed in thisembodiment. The backup processing illustrated in FIG. 9 is performed by:the CPU 11 of the management server 10 when the CPU 11 operatesaccording to a program stored in the storage 12; and the controller 21when the controller 21 operates according to a program stored in thecontroller 21.

As illustrated in FIG. 9, the CPU 11 of the management server 10 obtainsknowledge of the present date and time using a real-time clock, a GPSsignal, or similar means, and determines whether backup time has come(S200). It will be assumed that the backup time is stored in advance inthe storage 12. When the CPU 11 has determined the backup time has notcome yet (S200: N), the processing at S200 is performed again.

When the CPU 11 determines that the backup time has come (S200: Y), theCPU 11 makes a demand to the controller 21 for the setting data (S201).The demand for the setting data may be made by transmittingpredetermined form data. When there are a plurality of controllers 21,the CPU 11 makes a demand to each of the controllers 21 for the settingdata at S201. It is to be noted that all the controllers 21 may notnecessarily be regarded as backup targets; some of the controllers 21may be regarded as backup targets.

Upon receipt of the demand for the setting data, the controller 21transmits setting data stored in a storage of the controller 21 (S202).At S202, the controller 21 transmits all the backup target setting datatogether with information for identifying the controller 21 (forexample, the name of the controller 21). It is to be noted that thebackup target may not necessarily be all the setting data stored in thecontroller 21; some of the setting data may be regarded as the backuptarget.

Upon receipt of the set data from the controller 21, the CPU 11 of themanagement server 10 stores the setting data into the controllerdatabase DB1 and obtains a backup of the setting data (S203). At S203,the CPU 11 stores the setting data by relating the setting data with thename of the controller 21 from which the setting data is transmitted,and obtains a backup of such setting data. In this respect, the CPU 11stores the present date and time as backup date and time.

The CPU 11 compares the setting data received at S203 (the latest backupof setting data) with a past backup of setting data (the most previousor earlier backup of setting data), and based on the comparison,determines whether a change has been made to the setting data (S204). AtS204, the CPU 11 determines whether program codes or parameter valuesmatch. This embodiment is regarding a case where the determination atS204 is “Yes” when a change is made to at least one piece of the settingdata. Another possible example is that the determination at S204 is“Yes” when a change is made to a particular piece of the setting data.Still another possible example is that the determination at S204 is“Yes” when the number of the setting data that is changed is outside areference range.

When the CPU 11 determines that a change is made to the setting data(S204: Y), the CPU 11 stores changed-unchanged information having afirst value into the controller database DB1 (S205). Then, the CPU 11transmits an electronic mail (S206) to the user, thus ending theprocessing. At S205, the CPU 11 sets a first value in thechanged-unchanged information of the controller 21 from which thesetting data is transmitted. Then, the CPU 11 stores the name of thechanged setting data. It is to be noted that at this time of theprocessing, the CPU 11 may obtain the change content information and thechange kind information and include the change content information andthe change kind information in the changed-unchanged information. AtS206, the CPU 11 transmits an electronic mail to a predetermined mailaddress. The destination of the electronic mail may be specified on anindividual controller 21 basis.

When the CPU 11 determines that no change is made to the setting data(S204: N), the CPU 11 stores changed-unchanged information having asecond value into the controller database DB1 (S207), thus ending theprocessing. At S207, the CPU 11 sets a second value in thechanged-unchanged information of the controller 21 from which thesetting data is transmitted. In this case, since no change has been madeto the setting data, no electronic mail is sent.

Alarm Occurrence Processing

FIG. 10 is a flow chart of alarm occurrence processing. The alarmoccurrence processing illustrated in FIG. 10 is performed by: the CPU 11of the management server 10 when the CPU 11 operates according to aprogram stored in the storage 12; the controller 21 when the controller21 operates according to a program stored in the storage of thecontroller 21; and the CPU 31 of the user terminal 30 when the CPU 31operates according to a program stored in the storage 32.

As illustrated in FIG. 10, first, the controller 21 determines whetheran alarm has occurred (S300). At S300, based on a motion status of thecontroller 21 or the robot 22, the controller 21 determines whether analarm occurrence condition is met. Details of this determinationprocessing are as described above.

When the controller 21 determines that an alarm occurs (S300: Y), thecontroller 21 transmits an alarm occurrence notification to themanagement server 10. The alarm occurrence notification shows that analarm occurs (S301). At S301, the controller 21 transmits the alarmoccurrence notification such that the alarm occurrence notificationincludes: the alarm occurrence date and time, which are the present dateand time; and the alarm code indicated by the alarm occurrence conditionthat is met.

Upon receipt of the alarm occurrence notification, the CPU 11 of themanagement server 10 updates the alarm occurrence information includedin the controller database DB1 (S302), and transmits an electronic mailto the user (S303). At S302, the CPU 11 stores, in the controllerdatabase DB1, the alarm occurrence information such that the alarmoccurrence information includes the alarm occurrence date and time andthe alarm code, which are included in the alarm occurrence notification.At S303, the CPU 11 prepares an electronic mail notifying that an alarmoccurs, and transmits the electronic mail to the address of the user.The electronic mail may include: the name of the controller 21 in whichthe alarm occurs; alarm code; alarm name; alarm occurrence time; and ahyperlink to the alarm list screen G2. The destination of the electronicmail may be specified on an individual controller 21 basis.

The CPU 31 of the user terminal 30 transmits a demand for displaying thealarm list screen G2 (S304). Upon receipt of the demand for displayingthe alarm list screen G2, the CPU 11 of the management server 10generates, based on the controller database DB1, data to be displayed onthe alarm list screen G2, and transmits the data to the user terminal 30(S305). At S305, the CPU 11 refers to the occurring alarm informationincluded in the controller database DB1; identifies the controller 21 inwhich the alarm occurs, alarm occurrence time, alarm code, and alarmname; and generates data to be displayed on the alarm list screen G2.

Upon receipt of the data to be displayed on the alarm list screen G2,the CPU 31 of the user terminal 30 causes the display 35 to display thealarm list screen G2 based on the received data (S306). The CPU 31receives a detection signal from the operation part 34 and, based on thedetection signal, determines whether an alarm displayed on the alarmlist screen G2 has been selected (S307).

When the CPU 31 determines that an alarm has been selected (S307: Y),the CPU 31 transmits a demand for displaying details of the selectedalarm on the alarm detail screen G3 (S308). It will be assumed that thedemand for displaying includes: the name of the controller 21 in whichthe alarm selected by the user occurs; alarm occurrence time; alarmcode; and alarm name.

Upon receipt of the demand for displaying the alarm detail screen G3,the CPU 11 of the management server 10 identifies, based on the relationdatabase DB2, setting data related to the alarm specified by the user(S309). Then, based on the controller database DB1, the CPU 11 generatesdata to be displayed on the alarm detail screen G3, and transmits thedata to the user terminal 30 (S310). At S309, the CPU 11 refers to therelation database DB2 and identifies the setting data made to related tothe name of the controller 21 and the alarm code that are included inthe demand for displaying. At S310, the CPU 11 refers to the controllerdatabase DB1; obtains a present version of the identified setting dataas of the alarm occurrence time and a previous version of the identifiedsetting data that is one version previous to the present version; andgenerates data to be displayed on the alarm detail screen G3.

Upon receipt of the data to be displayed on the alarm detail screen G3,the CPU 31 of the user terminal 30 causes the display 35 to display thealarm detail screen G3 based on the received data (S311), thus endingthe processing.

As has been described hereinbefore, when the industrial machinemanagement system 1 determines that a change has been made to thesetting data of the controller 21, the industrial machine managementsystem 1 obtains change information regarding the change. When apredetermined event is determined as occurring in the controller 21, theindustrial machine management system 1 identifies and outputs changeinformation related to the predetermined event. Thus, the industrialmachine management system 1 provides information useful for an analysisfor what caused the predetermined event in the controller 21, thusassisting the user in the user's analysis for what caused thepredetermined event. For example, if someone has changed the settingdata without the user's knowing, causing a predetermined event to occur,the user is able to obtain knowledge of change information related tothe predetermined event. Thus, the industrial machine management system1 effectively assists the user in the user's analysis for what causedthe predetermined event.

Also, when the management server 10 determines that a predeterminedevent occurs in the controller 21, the management server 10 identifiesand outputs change content information related to the event that occurs.This makes the user readily aware of which changes have been made towhich parts of the setting data and aware of which of the changes hascaused the predetermined event. Thus, the management server 10effectively assists the user in the user's analysis for what caused thepredetermined event to occur in the controller 21. For example, when apredetermined event (such as an alarm) occurs in the controller 21, itis possible that the event has something to do with a change made to aparticular position on the setting data. In light of this, outputtingthe change content information effectively assists the user in theuser's analysis for the cause of the event.

Also, when the management server 10 determines that a predeterminedevent occurs in the controller 21, the management server 10 identifiesand outputs change kind information related to the event that occurs.This makes the user readily aware of which changes have been made towhich kinds of setting data and aware of which of the changes has causedthe predetermined event. Thus, the management server 10 effectivelyassists the user in the user's analysis for what caused thepredetermined event to occur in the controller 21. For example, when apredetermined event (such as an alarm) occurs in the controller 21, itis possible that the event has something to do with a change made to aparticular kind of the setting data. In light of this, outputting thechange kind information effectively assists the user in the user'sanalysis for the cause of the event.

Also, when an alarm occurs in the controller 21, there is a case where achange made to the setting data of the controller 21 has something to dowith the alarm. In light of this, outputting change informationeffectively assists the user in the user's analysis for the cause of thealarm.

Also, the kinds of events occurrable in the controller 21 may be causedby different kinds of setting data. In light of this, when a kind ofevent occurs in the controller 21, change information of the kind ofsetting data related to the kind of event is identified and output.Thus, change information that is based on the kind of event that occursis provided. This effectively assists the user in the user's analysisfor what caused the event.

Also, for each of the plurality of kinds of events, a kind of settingdata that has been specified by a user is registered. This enables theuser himself/herself to specify the kind of setting data related to thekind of event that occurs in the controller 21. Thus, the user is ableto, on an individual event kind basis, specify a kind of setting datathat the user wishes to analyze. This effectively assists the user inthe user's analysis for what caused an event.

Also, once setting data has been collected from the controller 21 forbackup purposes, change information can also be output. That is, it isnot necessary to collect the setting data only for the purpose ofoutputting change information. This more efficiently saves theprocessing load on the controller 21 and the management server 10 andthe communication load on the network.

5. Modifications

Modifications of the above-described embodiments will be describedbelow.

FIG. 11 is a functional block diagram of a modification of theabove-described embodiment. As illustrated in FIG. 11, the managementserver 10 includes a recording part 108, a recorded kind identifyingpart 106F, a role identifying part 106G, and an another-machineidentifying part 106H. These functions are mainly implemented by the CPU11.

Modification 1

In the above-described embodiment, the user manually registers arelationship between an alarm code and a piece of setting data. Inmodification 1, a relationship between an alarm that occurs in thecontroller 21 and setting data that was changed most recently isstatistically analyzed, and a relationship between an alarm code andrelated setting data is identified.

FIG. 12 illustrates an example relation database DB2 of modification 1.As illustrated in FIG. 12, the relation database DB2 stores controllernames, alarm codes, alarm names, and degrees of relation of settingdata. That is, the relation database DB2 stores a degree of relation ofsetting data on an individual alarm basis.

As used herein, the term “degree of relation” refers to how closely apiece of setting data is related to an alarm. A higher degree ofrelation indicates a higher probability of relation to an alarm. Thedegree of relation is updated upon occurrence of an alarm and based on aversion of setting data to which a most recent change (an m-th change (mis a natural number)) was made. For example, as in is greater at thetime of occurrence of an alarm, the degree of relation is higher.

In modification 1, the management server 10 includes the recording part108 and the recorded kind identifying part 106F. When one alarm among aplurality of kinds of alarms is determined as occurring, the recordingpart 108 records, in relation to the kind of the one alarm, a kind ofsetting data that was changed at least most recently. Since a kind ofalarm is identified by an alarm code, the recording part 108 records, inrelation to an alarm code, a kind of setting data that was changed atleast most recently.

As used herein, the term “setting data that was changed at least mostrecently” refers to a version of setting data to which an m-th change,at the latest, was made as of time after the alarm occurred. Inmodification 1, m is set at 1. In another possible example, in may betwo or more. Specifically, the kind of setting data that may be recordedare, with the time at which the alarm occurred taken as a reference: aversion of setting data to which a most recent change was made; and aversion of setting data to which a second or later change was made.

In modification 1, the degree of relation of setting data is set on anindividual alarm code basis. By increasing the degrees of relation ofpieces of setting data, the recording part 108 records a kind of settingdata that was changed at least most recently. For example, when an alarmoccurs, the recording part 108 refers to the changed-unchangedinformation included in the controller database DB1, and identifies thename of the setting data to which the most recent, in-th change wasmade. Then, the recording part 108 increases the degree of relation ofthe setting data made to be related to the alarm code of the alarm thatoccurs.

In modification 1, the amount by which to increase the degree ofrelation at a time is one. The amount, however, may be any other amount,such as two or more. In one example, when m is two or more, therecording part 108 may increase the degree of relation by giving agreater weight to a piece of setting data closer to the time at whichthe alarm occurred. In another example, when past two changes made tosetting data after the time of alarm occurrence are considered, therecording part 108 may add two to the degree of relation of the mostrecent version of setting data, and may add one to the degree ofrelation of the second most recent version of setting data. This ensuresthat as the time at which a piece of setting data was changed is closerto the time at which an alarm occurred, the degree of relation of thepiece of setting data to the alarm occurrence increases.

When one alarm among a plurality of kinds of alarms is determined asoccurring after the recording part 108's recording, the recorded kindidentifying part 106F identifies, based on the recorded content recordedby the recording part 108's recording, change information of the kind ofsetting data related to the kind of the alarm. In modification 1, thecontent of the recording part 108's recording is recorded in therelation database DB2. Therefore, based on the relation database DB2,the recorded kind identifying part 106F identifies the kind of settingdata related to the alarm. For example, the recorded kind identifyingpart 106F may identify a piece of setting data having the highest degreeof relation, or may identify a predetermined series of setting dataarranged in decreasing order of degree of relation. The processing afterthe related setting data has been identified is as described in theabove embodiment. By this processing, the alarm detail screen G3displays the change information of the setting data that has beenidentified.

Thus, in modification 1, when one alarm among a plurality of kinds ofalarms is determined as occurring in an industrial machine, themanagement server 10 records, in relation to the kind of the one alarm,a kind of setting data that was changed at least most recently. Then,based on what has been recorded, the management server 10 identifieschange information of a kind of setting data related to the kind of theone alarm that occurs in the industrial machine. Thus, the changeinformation is output based on a statistical analysis of a relationshipbetween an alarm that occurred in the past and the kind of setting datathat is changed. This ensures that the change information provided isregarding a piece of setting data that is more closely related to thealarm that occurs in the industrial machine. This effectively assiststhe user in the user's analysis for what caused the alarm.

Modification 2

It is possible that setting data related to an alarm varies depending onthe role of the controller 21. As used herein, the term “role” may referto the application in which the controller 21 is used. For example, whenthe controller 21 machines a workpiece, the kind of machining performedby the controller 21 corresponds to the role of the controller 21. Inother words, the kind of step that the controller 21 is in charge ofcorresponds to the role of the controller 21. It is possible to, foreach of roles of the controllers 21, register a piece of setting datarelated to an alarm and to identify a piece of setting datacorresponding to the role of the controller 21 in which an alarm occurs.

The following description of modification 2 is regarding an example inwhich the robot 22 is used in food processing. Specifically, it will beassumed that a plurality of production lines exist in a facility andthat four steps, namely, material generating step, shaping step, heatingstep, and wrapping step are performed on each of the production lines.On each of the production lines, four sets of controllers 21 and robots22 are used to perform the corresponding step. It is often the case thatwhat causes an alarm in the controller 21 working on the materialgenerating step on one of the production lines, A, is the same as whatcauses an alarm in the controller 21 working on the material generatingstep on another one of the production lines, B. Similarly, it is oftenthe case that the shaping step, the heating step, and the wrapping stepeach have a unique situation in which an alarm is caused to occur in thecontroller 21 on each production line. In light of the considerationsabove, related setting data may be registered for each role of thecontroller 21 (for each step that the controller 21 is in charge of).

In modification 2, the management server 10 includes the roleidentifying part 106G. When an alarm is determined as occurring, therole identifying part 106G identifies, based on the role of thecontroller 21, change information related to the alarm. In modification2, it will be assumed that the roles of the controllers 21 are stored inthe controller database DB1.

As described in the above embodiment, when the user manually registerssetting data related to an alarm, an example of how data is stored inthe relation database DB2 is as illustrated in FIG. 7. It is to benoted, however, that the above embodiment is regarding a case wheresetting data related to an alarm is registered for each controller 21(on an individual controller 21 basis), while modification 2 isregarding a case where setting data related to an alarm is registeredfor each role of the controller 21. In the food processing exampledescribed earlier, setting data related to an alarm is registered foreach step (on an individual step basis).

When an alarm occurs in a controller 21, the role identifying part 106Grefers to the controller database DB1, and identifies the role of thecontroller 21 in which the alarm occurs. Then, the role identifying part106G refers to the relation database DB2. Then, based on the registeredcontent corresponding to the role that has been identified, the roleidentifying part 106G identifies change information related to thealarm. For example, the role identifying part 106G identifies settingdata made to be related to both the role of the controller 21 in whichthe alarm occurs and the alarm code of the alarm. The processing afterthe related setting data has been identified is as described in theabove embodiment. By this processing, the alarm detail screen G3displays the change information of the setting data that has beenidentified.

While modification 2 is regarding an example in which the user manuallyspecifies setting data related to an alarm, it is possible tostatistically analyze setting data related to an alarm, as inmodification 1. In this case as well, the processing performed inmodification 2 is applicable. In the statistical analysis configuration,an example of how data is stored in the relation database DB2 is asillustrated in FIG. 12. The relation database DB2 stores the degree ofrelation of each piece of setting data for each role of the controller21. When an alarm occurs in a controller 21, the recording part 108updates a degree of relation made to be related to the role of thecontroller 21. When an alarm is determined as occurring, the roleidentifying part 106G identifies, based on the degree of relationrelated to the role of the controller 21, setting data related to thealarm. The processing of identifying setting data based on the degree ofrelation is as described in modification 1.

Thus, in modification 2, when a predetermined alarm occurs in thecontroller 21, the management server 10 identifies change informationbased on the role of the controller 21 and outputs the changeinformation. This ensures that information useful for analyzing whatcaused the predetermined alarm to occur in the controller 21 isprovided. This effectively assists the user in the user's analysis forwhat caused the predetermined alarm.

Modification 3

It is possible that an alarm occurring in a controller 21 in charge of astep is not attributed to the setting data of the controller 21 itselfbut is attributed to the setting data of another controller 21 in chargeof a step performed before or after the above step. In light of this,when an alarm occurs in a controller 21, the setting data of anothercontroller 21 may be displayed as setting data related to the alarm. Inthe food processing example described in modification 2, an alarmoccurring in the controller 21 in charge of the shaping step may beattributed to the setting data of the controller 21 in charge of thematerial generating step, which is a step previous to the shaping step.In light of this, when an alarm occurs in the controller 21 in charge ofthe shaping step, it is possible to display change information of thesetting data of the controller 21 in charge of the material generatingstep.

In this modification, the management server 10 includes theanother-machine identifying part 106H. It will be assumed that aplurality of controllers 21 belong to the identical production line.When an alarm is determined as occurring in one controller 21 among theplurality of controllers 21, the another-machine identifying part 106Hidentifies change information of another controller 21. The anothercontroller 21 may be any controller 21 that belongs to the productionline to which the controller 21 in which the alarm occurs belongs. Inone example, the another-machine identifying part 106H may identifychange information of all the other controllers 21 belonging to theidentical production line. In another example, the another-machineidentifying part 106H may identify change information of some othercontrollers 21 belonging to the identical production line. In anotherexample, the another-machine identifying part 106H may identify: changeinformation of another controller 21 in charge of the step performedprevious to the step that the controller 21 in which the alarm occurs isin charge of; and change information of another controller 21 in chargeof the step performed after the step that the controller 21 in which thealarm occurs is in charge of. In another example, the another-machineidentifying part 106H may identify either one of these two pieces ofchange information. In another example, the another-machine identifyingpart 106H may identify change information of all the other controllers21, instead of change information of the controllers 21 in charge of theprevious and next steps.

Thus, when a predetermined event occurs in the controller 21, anothercontroller 21 belonging to the identical production line may beattributed to the predetermined event. In light of this, in modification3, the management server 10 outputs change information of the anothercontroller 21. This ensures that information useful for analyzing whatcaused the predetermined event is provided. This effectively assists theuser in the user's analysis for what caused the predetermined event.

Modification 4

The above-described described modifications may be combined with eachother.

In another example, the management server 10 may not necessarily collectthe setting data for backup purposes but may collect the setting data atany desired timing such as time when an alarm occurs. While in theabove-described embodiment and modifications the main functions areimplemented by the management server 10, the main functions may beassigned to a plurality of computers.

Obviously, numerous modifications and variations of the presentdisclosure are possible in light of the above teachings. It is thereforeto be understood that within the scope of the appended claims, thepresent disclosure may be practiced otherwise than as specificallydescribed herein.

What is claimed is:
 1. An industrial machine management system,comprising: circuitry configured to collect changeable setting data ofan industrial machine, determine, based on the setting data at each timepoint of a plurality of time points, whether a change has been made tothe setting data, obtain change information regarding the change whenthe change is determined as having been made to the setting data,determine whether a predetermined event has occurred in the industrialmachine, identify, when the predetermined event is determined as havingoccurred, the change information such that the change information isrelated to the predetermined event, and output the change informationthat is identified.
 2. The industrial machine management systemaccording to claim 1, wherein the circuitry is further configured toobtain change content information as the change information when thechange is determined as having been made to the setting data, the changecontent information regarding a content of the change made to thesetting data, identify, when the predetermined event is determined ashaving occurred, the change content information such that the changecontent information is related to the predetermined event, and outputthe change content information that has been identified.
 3. Theindustrial machine management system according to claim 1, wherein thesetting data includes a plurality of kinds of setting data changeable inthe industrial machine, and the circuitry is further configured toobtain, when the change is determined as having been made to the settingdata, change kind information as the change information, the change kindinformation regarding a kind of the setting data to which the change hasbeen made, identify, when the predetermined event is determined ashaving occurred, the change kind information such that the change kindinformation is related to the predetermined event, and output the changekind information that has been identified.
 4. The industrial machinemanagement system according to claim 1, wherein the circuitry is furtherconfigured to determine whether an alarm has occurred as thepredetermined event in the industrial machine, and identify, when thealarm is determined as having occurred, the change information such thatthe change information is related to the alarm.
 5. The industrialmachine management system according to claim 1, wherein the setting dataincludes a plurality of kinds of setting data changeable in theindustrial machine, and the predetermined event is one of a plurality ofkinds of events occurrable in the industrial machine, and the circuitryis further configured to identify, when one kind of event, among theplurality of kinds of events, is determined having occurred, the changeinformation of one kind of setting data among the plurality of kinds ofsetting data such that the one kind of setting data is related to theone kind of event.
 6. The industrial machine management system accordingto claim 5, wherein the circuitry is further configured to register, foreach of the plurality of kinds of events, a kind of setting data, amongthe plurality of kinds of setting data, that has been specified by auser, and identify, when one kind of event among the plurality of kindsof events is determined as having occurred, the change information ofone kind of setting data among the plurality of kinds of setting databased on a registered content such that the one kind of setting data isrelated to the one kind of event.
 7. The industrial machine managementsystem according to claim 5, wherein the circuitry is further configuredto relate, when one kind of event among the plurality of kinds of eventsis determined as having occurred, the one kind of event to a kind ofsetting data, among the plurality of kinds of setting data, to which thechange has been made most recently, and record the kind of setting data,and identify, when the one kind of event is determined as havingoccurred after the circuitry recorded the kind of setting data, thechange information of one kind of setting data among the plurality kindsof setting data based on a recorded content recorded by the circuitrysuch that the one kind of setting data is related to the one kind ofevent.
 8. The industrial machine management system according to claim 1,wherein the circuitry is further configured to identify, when thepredetermined event is determined as having occurred, the changeinformation based on a role of the industrial machine such that thechange information is related to the predetermined event.
 9. Theindustrial machine management system according to claim 1, wherein theindustrial machine is one of a plurality of industrial machinesbelonging to an identical production line, and the circuitry isconfigured to identify, when the predetermined event is determined ashaving occurred in one industrial machine among the plurality ofindustrial machines, the change information of another industrialmachine among the plurality of industrial machines.
 10. The industrialmachine management system according to claim 1, wherein the circuitry isfurther configured to store, as a backup, the collected setting data,and determine, based on the backup, whether the change has been made tothe setting data.
 11. A method for managing an industrial machine,comprising: collecting changeable setting data of the industrialmachine; determining, based on the setting data at each time point of aplurality of time points, whether a change has been made to the settingdata; obtaining change information regarding the change when the changeis determined as having been made to the setting data; determiningwhether a predetermined event has occurred in the industrial machine;identifying, when the predetermined event is determined as havingoccurred, the change information such that the change information isrelated to the predetermined event; and outputting the changeinformation that is identified.
 12. A non-transitory computer-readablestorage medium storing a program for causing a computer to execute amethod for managing an industrial machine, the method comprising:collecting changeable setting data of the industrial machine;determining, based on the setting data at each time point of a pluralityof time points, whether a change has been made to the setting data;obtaining change information regarding the change when the change isdetermined as having been made to the setting data; determining whethera predetermined event has occurred in the industrial machine;identifying, when the predetermined event is determined as havingoccurred, the change information such that the change information isrelated to the predetermined event; and outputting the changeinformation that is identified.
 13. The industrial machine managementsystem according to claim 3, wherein the setting data includes aplurality of kinds of setting data changeable in the industrial machine,and the circuitry is further configured to obtain, when the change isdetermined as being made to the setting data, change kind information asthe change information, the change kind information regarding a kind ofthe setting data to which the change has been made, identify, when thepredetermined event is determined as having occurred, the change kindinformation such that the change kind information is related to thepredetermined event, and output the change kind information that hasbeen identified.
 14. The industrial machine management system accordingto claim 2, wherein the circuitry is further configured to determinewhether an alarm has occurred as the predetermined event in theindustrial machine, and identify, when the alarm is determined as havingoccurred, the change information such that the change information isrelated to the alarm.
 15. The industrial machine management systemaccording to claim 3, wherein the circuitry is further configured todetermine whether an alarm has occurred as the predetermined event inthe industrial machine, and identify, when the alarm is determined ashaving occurred, the change information such that the change informationis related to the alarm.
 16. The industrial machine management systemaccording to claim 2, wherein the setting data includes a plurality ofkinds of setting data changeable in the industrial machine, and thepredetermined event is one of a plurality of kinds of events occurrablein the industrial machine, and the circuitry is further configured toidentify, when one kind of event, among the plurality of kinds ofevents, is determined having occurred, the change information of onekind of setting data among the plurality of kinds of setting data suchthat the one kind of setting data is related to the one kind of event.17. The industrial machine management system according to claim 3,wherein the setting data includes a plurality of kinds of setting datachangeable in the industrial machine, and the predetermined event is oneof a plurality of kinds of events occurrable in the industrial machine,and the circuitry is further configured to identify, when one kind ofevent, among the plurality of kinds of events, is determined hasoccurred, the change information of one kind of setting data among theplurality of kinds of setting data such that the one kind of settingdata is related to the one kind of event.
 18. The industrial machinemanagement system according to claim 4, wherein the setting dataincludes a plurality of kinds of setting data changeable in theindustrial machine, and the predetermined event is one of a plurality ofkinds of events occurrable in the industrial machine, and the circuitryis further configured to identify, when one kind of event, among theplurality of kinds of events, is determined as having occurred, thechange information of one kind of setting data among the plurality ofkinds of setting data such that the one kind of setting data is relatedto the one kind of event.
 19. The industrial machine management systemaccording to claim 13, wherein the setting data includes a plurality ofkinds of setting data changeable in the industrial machine, and thepredetermined event is one of a plurality of kinds of events occurrablein the industrial machine, and the circuitry is further configured toidentify, when one kind of event, among the plurality of kinds ofevents, is determined as having occurred, the change information of onekind of setting data among the plurality of kinds of setting data suchthat the one kind of setting data is related to the one kind of event.20. The industrial machine management system according to claim 14,wherein the setting data includes a plurality of kinds of setting datachangeable in the industrial machine, and the predetermined event is oneof a plurality of kinds of events occurrable in the industrial machine,and the circuitry is further configured to identify, when one kind ofevent, among the plurality of kinds of events, is determined as havingoccurred, the change information of one kind of setting data among theplurality of kinds of setting data such that the one kind of settingdata is related to the one kind of event.